Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The PR allows us to keep track of QoS of each
Entity
withinGraphCache
. Previously topics with same name and type were considered equivalent. Now, theTopicMap
contains the nestedTopicTypeMap
(renamed fromTopicDataMap
) which in turn contains the nestedTopicQoSMap
. The key for theTopicQoSMap
, is a string serialization ofrmw_qos_profile_t
which we already use to include QoS information in liveliness tokens.With this change, we can keep track of the exact QoS settings used by entities within the
GraphCache
which makes it easier to check for QoS events.Also updated in this PR:
TopicMap
objects within aGraphNode
andgraph_topics_/graph_services_
caches.